refs: Agoric#9281

## Description
AsyncFlow requires that everything passing the membrane is durable. This makes the facade objects durable to conform.

Doing so for `localChainFacade` is deferred so we can get this into master sooner, to aid @erights 's Agoric#9521 .

### Security Considerations
none
### Scaling Considerations

Exo for each chain and each account

### Documentation Considerations
none
### Testing Considerations

Existing coverage

### Upgrade Considerations
none, not yet deployed

refs: Agoric#9281

## Description

AsyncFlow requires that everything passing the membrane is durable. This makes the facade objects durable to conform.

Following Agoric#9529 

### Security Considerations
none

### Scaling Considerations
Exo for each chain and each account


### Documentation Considerations
none

### Testing Considerations
Existing coverage


### Upgrade Considerations
not yet deployed

Vat termination now makes the kernel do a console.log like:

 `kernel terminating vat v6 (failure=true)`

Vat upgrade now announces the start of the upgrade process with:

 `attempting to upgrade vat v6 from incarnation 0 to source b1-..`

in addition to announcing the success or failure of the upgrade

 `vat v6 upgraded from incarnation 0 to 1 with source b1-..`
 or
 `WARNING: vat v6 failed to upgrade from incarnation 0 (startVat)`

- refs: Agoric#9449

- refs: Agoric#9449

- refs: Agoric#9449

refs: Agoric#9449 

## Description

- [x] convert icqConnectionKit to return vows
- [x] convert Orchestration service (`service.js`) to return vows 
- [x] convert chainAccountKit to return vows

### Security Considerations


### Scaling Considerations

These changes are necessary towards supporting using `orchestration` in `asyncFlow`. 


### Documentation Considerations


### Testing Considerations


### Upgrade Considerations

refs: Agoric#9281 

## Description

AsyncFlow requires that everything passing the membrane is durable. This makes the ChainHub durable by making it an Exo.


### Security Considerations
none

### Scaling Considerations

It's a singleton, because there will only be one per vat.

### Documentation Considerations
none

### Testing Considerations
Existing coverage

### Upgrade Considerations
Not yet deployed.

Now that it's an Exo, we have to consider its state an upgradability. We expect to make a new one on each vat invocation. The only state it has is cache of AgoricNames and data supplied by the contract.

fix(liquidationVisibility): fix dependency errors

Refs: #24

fix(liquidationVisibility): fix race condition when running tests concurrently

fix(liquidationVisibility): fix test-vaultLiquidation.js

author anilhelvaci <anilhelvaci96@gmail.com> 1708371947 +0300
committer anilhelvaci <anilhelvaci96@gmail.com> 1708960452 +0300

fix(liquidationVisibility): lint fix

fix(liquidationVisibility): lint fix

fix(liquidationVisibility): lint fix

fix(liquidationVisibility): fix paths

fix(liquidationVisibility): lint and type fixes

fix(liquidationVisibility): lint fixes

…date dependencies

…ty (WiP)

…ara instead of state.

Refs: #15

…e for readability (WiP)

fix(liquidationVisibility): fix unit tests after rebase updates

…ests

Refs: #35

Refs: #35

…ty` in core-eval

Refs: #35

…s` and update tests accordingly

Refs: #35

Refs: #35

…ove `writeLiqVisibility`

Refs: #35

…onVisibilityWriters` resulted with below changes;

* Use `Promise.all` instead of `allValuesSettled`
* Remove `liq-rejected-schedule` and `liq-rejected-timestampStorageNode` as we don't need to handle those cases anymore
* Write an error message in postAuction and auctionResults recorder kits in the case of an error in distributing plans

Refs: #35

…lated artifacts.

Refs: #35

Refs: #35

Refs: #35

Refs: #35

Refs: #35

TODO: Update bootstrap tests as well

Refs: #35 #36

…sibility method and respective snapshot

…auctionResult with new data fields

Ref: #35 and #36

Refs: #35